|
In the field of IPv6 deployment, IPv6 brokenness is bad behavior seen in tunneled or dual stack IPv6 deployments where unreliable or bogus IPv6 connectivity is chosen in preference to working IPv4 connectivity. This often results in long delays in web page loading, where the user has to wait for each attempted IPv6 connection to time out before the IPv4 connection will be tried. These timeouts may range from being near-instantaneous in the best cases, to taking anywhere between four seconds to three minutes.〔(【引用サイトリンク】title=IPv6 transition experiences ) presented at NANOG 50〕 == Brokenness == As of May 2011, IPv6 brokenness as measured by instrumenting a set of mainstream Norwegian websites was down to ~0.015%,〔(【引用サイトリンク】title=IPv6 dual-stack client loss in Norway )〕 most of which was caused by older versions of Mac OS X which would often prefer non-working IPv6 connectivity when it was not justified.〔(【引用サイトリンク】title=Measuring and combating IPv6 brokenness ), presented at RIPE 61, Rome, November 2010〕 This behavior was fixed in Mac OS X 10.6.5, and is likely to decline further as Mac OS X 10.6.5 and subsequent versions roll out to a wider audience. However, there was no upgrade path for PowerPC-based Macs. The main remaining problem for Mac OS X was the presence of rogue routers, such as wrongly configured Windows Internet Connection Sharing devices pretending to have IPv6 connectivity, while 6to4 tunneled IPv6 traffic is blocked at a firewall. Another problem was pre-10.50 versions of Opera. Following World IPv6 Day in July 2011, there were reports of a substantial reduction in IPv6 brokenness as a result of that experiment. In the year following the trial, but prior to the World IPv6 Launch date, brokenness levels were reported to have risen slowly back upwards again towards 0.03%. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「IPv6 brokenness and DNS whitelisting」の詳細全文を読む スポンサード リンク
|